Skip to content

Crashlytics exception handler #6266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 10 commits into from
Closed

Conversation

themiswang
Copy link
Contributor

Merge back to main

themiswang and others added 10 commits August 19, 2024 14:20
we are sending a task within a task for common worker which cause the
async behavior, remove the re-submitting task for report finalization
Avoid `Task`s in `checkForPreviousCrash`. This is a step towards
removing the nasty `awaitEvenIfOnMainThread`.
Deprecate `awaitEvenIfOnMain`. Next PR will be to drain the worker and
remove this util.
Adjust time out and disk worker as discussed. This moves some things off
the disk worker, but we plan to put them back after more refactoring.
Make init suspend on settings only, not on race. This allows us to avoid
having a separate queue just for init and settings.

If the app has unsent reports, but data collection and send unsent
reports both have not been triggered, still let user actions queue up.
Add a precondition check for not main thread. This is more useful when
we just want to enforce not main thread, not a specific thread.
Make doBackgroundInitializationAsync submit a callable instead of submit
task

Submit task results in a blocking behaviour when `SettingsTask` cannot
be resolved during initialization
Remove un-necessary task return
@themiswang themiswang closed this Sep 17, 2024
@firebase firebase locked and limited conversation to collaborators Oct 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants